Descrição

Nos últimos 6 meses, mapeei todos os parcómetros e áreas de estacionamento pago com duração limitada na cidade do Funchal, na Ilha da Madeira, como parte do projeto Parking in Portugal. Em algumas edições, utilizei o hashtag #portugal-estacionamento.

Para este projeto, foram úteis o aplicativo de uso gratuito iParque Driver, que oferece um mapa que indica as ruas que têm lugares de estacionamento pago (coloridas dependendo da zona), e as imagens aéreas da Ilha da Madeira de 2023, de 10 cm de resolução. Com estas indicações, fui a pé a cada um dos parcómetros, tirei uma foto da informação do parcómetro, e, logo em casa, com ajuda das imágens aéreas, adicionei os nós dos parcómetros com a sua informação (com uma precisão de, como máximo, 3 metros) e desenhei as áreas de estacionamento, também com a sua informação. A imagem seguinte é um exemplo da informação disponibilizada em um parcómetro:

(exemplo do nó osm.org/node/13568145429/.)

Zonas

… See full entry

Saya sedang memulai proyek untuk menambahkan tag name:id pada objek place=* di wilayah Jepang, Korea Selatan, dan Korea Utara. Tujuannya adalah mempermudah pengguna Indonesia dalam mencari dan mengenali nama tempat di Asia Timur sesuai dengan ejaan dan istilah administratif yang lazim (seperti Prefektur dan Provinsi).

Untuk saat ini, penyuntingan hanya dilakukan pada level Node. Objek berupa Relation (seperti batas administrasi) belum termasuk dalam cakupan kerja saya saat ini karena batasan workflow teknis.

---

Localizing place names (name:id) in Japan and the Koreas

I am starting a project to add the name:id tag to place=* objects in the Japan, South Korea, and North Korea regions. The purpose is to assist Indonesian users in searching for and recognizing place names in East Asia according to common spellings and administrative terms (such as Prefecture and Province).

For now, editing is only being performed at the Node level. Relation objects (such as administrative boundaries) are not yet included in my current scope of work due to technical workflow limitations.

Hello, I’m Aidan Kaita Saka from Tanzania 🇹🇿. An active youth mapper dedicated to improving maps for my community. I enjoy contributing roads, buildings, places, and useful local information to help people navigate better. Proud to support OpenStreetMap and community development.

Regarding Lougheed Highway in Coquitlam, BC, Canada: Nothing along Lougheed between Sage Place and Schoolhouse is accessible to foot traffic, but much of it claims to be, despite the significant danger. Lougheed appears to be editable in many sections, and I don’t know how to change the entire strip easily. Can someone help? Thank you!

Translations into the following languages have been added:

• English
• German
• Italian
• Slovak
• Russian

There are a lot of German speaking people in OSM, so this should help :)

Not much strings though :) There are also several validation messages, but there are just 32 lines total.

Just in case you would like to translate the plugin in any other language, here is the pot file.

We do not have any web UI for translations, but you can use PoEdit instead.

Because sometimes you want to see less rather than more, I created this. It’s the railway information from the existing transportation layer of the SVE01 schema, together with railway stations, places and water as needed for context.

One thing that it does is to distinguish between regular transportation railway stations and tourist ones.

Freight lines are de-emphasised (see here and disused and abandoned railways are shown in a barely-discernable grey.

The source of the style is here but that is just a subset of the “show everything” style for this schema here.

RETEX: My Journey into RTK

(text translated from my original entry in french using Chatgpt)

to be continued, perhaps:

• journal entry (coming soon): Existential questions about my encounter with Panoramax
• journal entry (coming soon): Mapping my village

I would like to point out that these journal entries are neither WIKI pages nor expert advice… They are simply accounts of lived experiences shared here for anyone who may be interested.

Why did I become interested in this topic?

During my urban recycling trekking (see previous journal entries), I photographed all the voluntary drop-off containers I came across, uploaded these photos to Panoramax, and added the Panoramax photo reference in OSM. This caused me no issues, as my goal was that, from the standard OpenStreetMap rendering layer, it would be easy (in this case, a simple click) to find the images.

I positioned the containers in OSM not based on the photo, but using aerial imagery and relevant environmental features (street intersections, buildings, etc.). This worked perfectly well until I noticed three things:

… See full entry

RETEX : RTK et moi

à suivre peut-être :

• entrée de journal (à venir) : Questions existentielles sur ma rencontre avec panoramax
• entrée de journal (à venir) : Cartographier mon village

Je rappelle que ces entrées de journal ne sont ni des pages de WIKI, ni des conseils d’expert … . Ce sont juste des comptes-rendus d’expérience vécue mises ici pour servir à toute personne intéressée.

Pourquoi me suis-je intéressé au sujet ?

Au cours de mon trekking urbain recyclage (voir entrées de journal précédentes), j’ai photographié tous les conteneurs de point d’apport volontaire que j’ai rencontrés, versé ces photos sur Panoramax et mis dans OSM la référence de la photo Panoramax. Cela ne m’a posé aucun problème, mon but étant qu’à partir du calque standard de rendu d’Openstreetmap, il soit aisé (en l’occurence un simple clic) de trouver les images.

Je positionnais dans OSM les conteneurs non pas à partir de la photo mais à partir de l’imagerie aérienne et des éléments pertinents de l’environnement (croisements de rues, bâtiments, …). Cela m’a parfaitement convenu jusqu’à trois constats :

… See full entry

My hood

Hello

You might have noticed that I have been maping this neighbourhood. Richmond. Why? Well Way: Richmond (1489761671) is small, historic and central with a mixed architectural heritage. You’ll find points of interest in the suburb of Q61359147. There are a number of offices and public (and private) education facilities. There’s no shortage of nearby recreation facilities either.

Mapping the hood with SPARQL.

In this post (which is in draft) I’m going to show how I go about creating a map of the hood

Take a specific place (Q61359147) as the center point Finds all nearby places within 10 km radius Filters them according to specific category (tourist attractions, bookshops ) Calculates how far each one is from the centre point and returns results from nearest to farthest.

Tourist Attractions (Q570116)

Let’s begin with a list. Are there tourist attractions (Q570116) near Richmond (Q61359147)? ~~~ SELECT DISTINCT ?place ?placeLabel ?location ?distance WHERE { hint:Query hint:optimizer “None” . wd:Q61359147 wdt:P625 ?arcLoc . #Change the location SERVICE wikibase:around { ?place wdt:P625 ?location . bd:serviceParam wikibase:center ?arcLoc . bd:serviceParam wikibase:radius “50” . } ?place wdt:P31/wdt:P279* wd:Q570116 . SERVICE wikibase:label { bd:serviceParam wikibase:language “en” . } BIND(geof:distance(?arcLoc, ?location) AS ?distance) } ORDER BY ASC(?distance) ~~~

Mapping the hood with Overpass Queries

You might want to explore [Overpass] (https://osm-queries.ldodds.com/) and see if you can finds a range of potentially interesting, historic or noteworthy locations. A lack of a wikidata link doesn’t mean that there is a wikidata entry to link to, or that the location should have one. This might be another useful starting point to find locally significant places. Credit to Leigh Dodds for all this information

… See full entry

Un petit tuto pour montrer comment importer du stationnement vélo issus d’une base de donnée en Opendata.

Ici la Communauté d’agglomération du Saint Quentinois vient de publier un jeux de données sur les aménagements cyclables.

https://www.data.gouv.fr/datasets/amenagements-cyclables-10

Avant de vérifier le linéaire avec OSM, on peut déjà importer les données ponctuels de stationnements vélo.

Avec QGIS, on importe les données, on vérifie leur homogénéités.

On peut suite traduire les champs et valeur en fonction de ce qui est attendu dans OSM.

exemple : champs “type” valeur ‘Appuis-vélos’ créer un champs “bicycle_parking” valeur ‘stands’ et on supprime ensuite le champs “type”

On supprime ensuite l’ensemble des champs inutiles dans OSM.

Dans QGIS, on importe également les stationnements existants déjà dans OSM, et on note bien les points en doublon, qu’il va falloir corriger après l’import.

Dans JOSM, on importe le fichier créer dans QGIS en .gpkg fichier - ouvrir

Puis on exporte après vérification.

Une fois importer dans OSM, on va retrouver les points en doublons et on effectue des fusions en prenant en compte les valeurs les plus à jours.

今日，到广州图书馆一游，记录一下

Accurate and precise updates

I’ve made excellent, accurate, and completely correct updates for o.s.m users in my area where I live, work, and spend most of my time. I’ve lived here for six years, I love my area completely, and I feel a true sense of belonging to it.

I’ve made the updates, but I don’t know when the new changes will appear in the map updates. There might be a delay in the update for some applications that use o.s.m.

Hello, i have an irrational fear of technology. Because i hate OSMwiki. i hate how things related to public transit is inconsistent. i hate how iD editor is inconsistent in giving necessary tags for PTv2. i don’t like stop positions. i don’t like iD editor not having an auto sort for relation members. i don’t like weird tagging schemes. i don’t like the OSM wiki having multiple different tags for very similar things without the wiki explaining them in terms of how the things that are being talked in OSMwiki is implemented in your country. i don’t like how convoluted it is for adding bus routes. harumph.

in another news, pt_assistant plugin for josm is a godsend. thank you kind stranger for this gift to humanity.

also, even if i added PTv2 compliant perfect bus routes, OSMand is still not able to properly show bus information on itself.

harumph.

please, someone save OSM and me.

The Virtual Institute for Sustainable Development - IVIDES.org® participated in “Mapping Together”, the virtual meeting of the MapYourGrid project

---

 

MapYourGrid logo © 2026 Open Energy Transition (OET).

 

The Virtual Institute for Sustainable Development - IVIDES.org® attended the virtual meeting of the MapYourGrid project, represented by its Chairwoman, Dra. Raquel Dezidério Souto, who participated in the meeting to learn about the project and understand its infrastructure and logical model.

The overall objective of the meeting was to demonstrate the structure of Wikidata and discuss improvements to the integration between the MapYourGrid web map, available at https://mapyourgrid.org/, and the Wikidata and Wikipedia structures, which are used to document objects related to the power distribution network mapped using OpenStreetMap.

You can see here the mental model of a workflow to this connection which was elaborated by Norman, Lacombe and other meeting attendees.

… See full entry

Ajout du parcours de “La Chartreuse” à Dijon

Par ici : osm.org/node/13731747305

Des infos par ici : https://www.discjonctes.fr

… See full entry

Membantu orang hendaknya ikhlas, dan tidak mengharap pujian atau apresiasi dari orang lain. Bantulah dengan bantuan yang terbaik. Dan tidak perlu kita mengungkit-ungkit bantuan yang kita berikan, berharap balasan dari ALLAH subhanahu wata’ala semata. Caranya mudah, bantuan yang engkau berikan itu ibarat yang engkau keluarkan dipagi hari. Dengan begitu engkau akan lupa, tidak ingat bantuan apa yang telah engkau berikan kepada orang lain

I had the opportunity to solely lead Nepal’s first Inclusive Mapping Week 2025 at Kathmandu University. What started as an idea became a week-long initiative bringing together over 400 participants to learn, map, and collaborate.

Throughout the program, we focused on both technical skills and real-world applications:

Humanitarian mapping using OpenStreetMap Remote sensing with Google Earth Engine Crisis mapping and spatial data use Field mapping with tools like Mapillary and OSM Tracker

One of the most meaningful aspects of this initiative was contributing mapping data to support earthquake-affected regions. It reinforced how open geospatial data can play a role in disaster preparedness and response.

As a young woman in the geospatial field, leading this initiative was both a challenge and a responsibility. Ensuring inclusivity and encouraging participation especially from women was at the core of this program.

Being recognized by The Annapurna Express for this work was a proud moment, but what matters most to me is the impact created through collective effort and open collaboration.

This experience taught me that:

Mapping is not just technical work—it creates real-world impact Leadership is about enabling others to contribute Inclusive communities build stronger, more meaningful maps

This is just the beginning of my journey with OpenStreetMap. Looking forward to contributing more, learning more, and building maps that represent people, communities, and realities. youthmappers blog; https://www.youthmappers.org/post/she-leads-we-map-nepal-s-first-inclusive-mapping-week-2025 The Annapurna Express: https://lnkd.in/g6ZSgBBq

ww

Introduction

Sometimes, we set out to solve one problem and arrive at a bunch of even greater discoveries along the way. This story starts with my curiosity about whether you can get a “GPS” track log underground - like in a tunnel or underground car park. GPS is our go-to tool for mapping most things that we can’t see on aerial imagery, but what can we do in places where GPS signals cannot be received? In the course of my investigation, I uncovered a few even more interesting insights:

• Even if you can code, it’s impressive what an off-the-cuff LLM prompt can build for you
• The openstreetmap.org site UI would work very differently had it been built in the smartphone era
• Capturing rich mapping data from stock vehicles with no extra hardware is feasible
• With relatively little effort, we can improve the effectiveness of GPS track log capture for OSM mapping

Oh, and I did manage to get that underground track log, but more on that anon…

Motivation: the desire to improve tunnel mapping

Mapping underground features in OSM can be challenging. Sometimes we are lucky - a tunnel or covered roadway may be a straight line between two known points on the surface. Perhaps the tunnel was built using cut-and-cover and we were able to establish the geometry during construction. But sometimes, we just have an underground linear feature with bends in it. We know where each end dives underground, but GPS signals cannot be received underground, so our traditional mapping approaches won’t help us.

Road tunnels, of course, are designed for vehicles, and many modern vehicles have moving map displays as part of a navigation system. When in a tunnel, many even show a plausible vehicle position that updates. Without GPS. How do they do that? They could simply infer movement along the mapped path of the road based on distance travelled. But they may also use more sophisticated dead-reckoning inferring direction from sensors. I have such a car. I wanted to find out.

… See full entry

In the second week (14th–19th February), we faced OSMMalawi. With no strategy to balance academics and mapping, I grew lazy. To overcome this, I wrote a sticky-note reminder on my laptop to push myself to map at least five tasks daily during breaks. By the end of the week, my contributions increased, and on 20th February, we celebrated another win, rising to 3rd place overall.

The third week (21st–26th February), the mapping match was against KabUyouth Mappers from Uganda. Bing imagery was unclear, but I adapted by using Google Earth references & comparing different imageries. My changesets piled up, promoting me from beginner to intermediate mapper. . We maintained the 3rd position but our captain organized a google meeting with Kingsley (one of the tournament organizers), who taught us valuable skills in both iD editor and JOSM.

By the fourth and fifth weeks (28th February–12th March), mapping had become part of my routine—even appearing in my dreams! Funny!!, am I right?

Despite some abrupt technical issues with OpenStreetMap login, we pushed through, won the game against YouthMappers Mukuba, and advanced to the next stage. By the end, we’re proudly ranked 4th among the top 10 contributing teams out of approx. 80 countries.

Thank you for reading my diary—I hope my journey inspires someone out there. Let’s map the world together! #SpatialMappers #AfricaMapCup2026. Cheers to all participants in this tournament, and please wish my team & I good for it’s still on going.